home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ETO Development Tools 4
/
ETO Development Tools 4.iso
/
Tools - Objects
/
Virtual User 1.0
/
Virtual User
/
VU.Help
< prev
Wrap
Text File
|
1991-01-25
|
5KB
|
101 lines
-
VU # Virtual User test tool
Usage:
VU [ option…]
Description:
Test tool for simulating one to many users. Runs user-interface level test scripts
on one or more target machines connected with AppleTalk.
Options:
To make control of multiple targets more flexible from the command line,
each of the following option flags (except -libs and -vers) can occur repeatedly and
be suffixed by a number. The number can be used to group options that apply to a
particular target.
-t targetname # Acquire control of the target on which the test is to be performed
# The target name is specified by giving its network path name, namely,
# <zone>:<target's Chooser User Name>
# If the target is on a local or private network then the zone name to be
# used is *
# Always enclose the target name within " or '
-a actorname # This specifies the name of an actor. An actor may be assigned a script and
# a target via the command line with the “-s” and “-t” options. If you do not
# specify an actor name from the command line, VU creates an actor
# anyway to run the script on the specified target.
# The actor’s name is assigned to the target address, i.e. “*:TargetMac”.
# If you haven’t specified a target from the command line, then you must specify
# an actor.
-s pathname # Pathname of the script file to be run against the corresponding target
-libs searchpath # This is used to specify the search path for VU to access task libraries.
# VU always looks for the declared libraries in the current directory first.
# If not found, it makes use of the search path provided on the command line
# (if any) and finally it checks the MPW variable “VULibraries” for a search
# path. By default this variable will be set to your “…:Virtual User:Libraries”
# folder by the provided “UserStartup•VU” MPW script (if you are using it).
-c # compile only. Used if you just want to test the syntax of your script,
# without running it. If you use this option you need not specify the target.
-l pathname # The name of the log file. The form of specification is same as in -s option.
# If you use this option, VU will write some important information about
# the test along with any error/warning messages in the specified file.
-dt # Write a diagnostic trace to the specified log file. Used only if you have
# specified the log file
-o pathname # Redirect the output of print and println statements from standard output to
# another file
-m mousespeed # Set the speed of mouse movement on the target (a positive integer)
-k keyboardrate # Set the maximum rate of keystrokes(type speed) on the target (a positive integer)
-cs # This option can be used to make VU's string matching case sensitive
-p patience # Set the patience of VU in exploring and manipulating the interface (a positive integer)
-retries n # Set the maximum number of retries on a network transaction (a positive integer)
-timeout n # Set the maximum number of seconds to wait for a network response (a positive integer)
-fail n # Set the maximum number of failures allowed. VU will abort on (n+1)th failure (a positive integer)
-vers # This is used to get the version information of VU.
Examples:
VU -s QuickLook.vu -t "*:MacSE30"
Executes the test script in QuickLook.vu on the machines whose chooser name is MacSE30 and
which resides in the local zone.
VU -t1 "*:gozer" -s1 "AdminTest.vu" -o1 "AdminTest.out" ∂
-t2 "*:chuck" -s2 "BusyWorkstation.vu" -o2 "BusyWS.out" -m2 0 -k2 50 ∂
-t3 "Farside:Twiddledee" -s2 "LazyWorkstation.vu" -o3 "LazyWS.out" -m3 1 -k3 5
Runs three different test scripts concurrently:
1) AdminTest.vu is run against gozer and the println output of that script
is sent to AdminTest.out.
2) BusyWorkstation.vu is run against chuck and the standard output of that
script is written to BusyWS.out. The mouse and keyboard rate for this test
are set to high values.
3) LazyWorkstation.vu is run against Twiddledee in the Farside zone and the
output is sent to LazyWS.out. The mouse and keyboard for this test are
set to slow values.
VU -a1 ‘Actor1’ -s1 ‘TestScript1.vu’ -l1 ‘TestScript1.log’ ∂
-o1 ‘TestScript1.out’ ∂
-a2 ‘Actor2’ -s2 ‘TestScript2.vu’ -l2 ‘TestScript2.log’ ∂
-o2 ‘TestScript2.out’ ∂
-libs ‘HD:Virtual User:MyScripts:Libraries:’
In the above command line either or both of the scripts can be using libraries.
The same search path is used for all scripts. Note that you are specifying only a
search path to locate the libraries. Some of your libraries may reside in this
specified directory and some may reside in your current directory and some may
even reside in another directory whose path name is specified by setting the MPW
shell variable “VULibraries”.
-